omitir warnings de 'availability' y 'wasm-notavail' #1847
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
edit: including explanation
the whole story on the 'availability' warnings are that there is a
.. availability::
command in the cpython docs that include, in some cases, stuff from the 'wasm-availability' file. So we have references "within" the 'availabiliy' command.as you can see, the entry has no mention of WASM or wahtsover in some entries, like "Unix, Windows",
but still will generate the following warning:
The reason that due to the internal reference to 'wasm-availability' , even in cases like this entry, where it's only Unix and Windows, for example:
https://docs.python.org/3.11/library/os.html?highlight=os#os.getenv
it generates the reference to the 'Availability' page, which inside has the 'wasm-availability' inside:
https://docs.python.org/3.11/library/intro.html#availability
Additionally, the
wasm-notavail
file is excluded to avoid the warning related to the file not being inclued in any index. We could have add:orphan:
to the file insidecpython
but we do it via the exclude patterns to avoid touching files on the submodule.